Communication between host systems using a socket connection and shared memories

ABSTRACT

Mechanisms for communication between host systems using a socket connection and shared memories are provided. With such socket-based communication, a work queue in the host systems may be used to listen for incoming socket initialization requests. A first host system that wishes to establish a socket communication connection with a second host system may generate a socket initialization request work queue element in its work queue and may inform the second host system that the socket initialization request work queue element is available for processing. The second host system may then accept or deny the request. If the second host system accepts the request, it returns the second half of the socket&#39;s parameters for use by the first host system in performing socket based communications between the first and second host systems.

BACKGROUND

1. Technical Field

The present application relates generally to an improved data processingsystem and method. More specifically, the present application isdirected to mechanisms for communication between host systems using asocket connection and shared memories.

2. Description of Related Art

Most modern computing devices make use of input/output (I/O) adaptersand buses that utilize some version or implementation of the PeripheralComponent Interconnect standard, which was originally created by Intelin the 1990s. The Peripheral Component Interconnect (PCI) standardspecifies a computer bus for attaching peripheral devices to a computermotherboard. PCI Express, or PCIe, is an implementation of the PCIcomputer bus that uses existing PCI programming concepts, but bases thecomputer bus on a completely different and much faster serialphysical-layer communications protocol. The physical layer consists, notof a bi-directional bus which can be shared among a plurality ofdevices, but of single uni-directional links, which are connected toexactly two devices.

FIG. 1 is an exemplary diagram illustrating a PCI Express (PCIe) fabrictopology in accordance with the PCIe specification. As shown in FIG. 1,the PCIe fabric topology 100 is comprised of a host processor (CPU) 110and memory 120 coupled to a root complex 130, which is in turn coupledto one or more of a PCIe endpoint 140 (the term “endpoint” is used inthe PCIe specification to refer to PCIe enabled I/O adapters), a PCIexpress to PCI bridge 150, and one or more interconnect switches 160.The root complex 130 denotes the root of an I/O hierarchy that connectsthe CPU/memory to the I/O adapters. The root complex 130 includes a hostbridge, zero or more root complex integrated endpoints, zero or moreroot complex event collectors, and one or more root ports. Each rootport supports a separate I/O hierarchy. The I/O hierarchies may becomprised of a root complex 130, zero or more interconnect switches 160and/or bridges 150 (which comprise a switch or PCIe fabric), and one ormore endpoints, such as endpoints 170 and 182-188. For more informationregarding PCI and PCIe, reference is made to the PCI and PCIespecifications available from the peripheral component interconnectspecial interest group (PCI-SiG) website at www.pcisig.com.

Today, PCI and PCIe I/O adapters, buses, and the like, are integratedinto almost every computing device's motherboard, including blades of ablade server. A blade server is essentially a housing for a number ofindividual minimally-packaged computer motherboard “blades”, eachincluding one or more processors, computer memory, computer storage, andcomputer network connections, but sharing the common power supply andair-cooling resources of the chassis. Blade servers are ideal forspecific uses, such as web hosting and cluster computing.

As mentioned above, the PCI and PCIe I/O adapters are typicallyintegrated into the blades themselves. As a result, the I/O adapterscannot be shared across blades in the same blade server. Moreover, theintegration of the I/O adapters limits the scalability of the linkrates. That is, the link rates may not scale with processor performanceover time. As of yet, no mechanism has been devised to allow PCI andPCIe I/O adapters to be shared by multiple system images across multipleblades. Moreover, no mechanism has been devised to allow the PCI andPCIe I/O adapters to be provided in a non-integrated manner for use by aplurality of blades in a blade server.

SUMMARY

In one illustrative embodiment, a method for communicating between afirst host system and a second host system is provided. The method maycomprise initializing a memory address space in a shared memory of thefirst host system to comprise an address range assigned to an endpointassociated with the second host system. The method may further comprisegenerating a work queue structure in the address range, posting, by thefirst host system, a socket initialization request to the work queuestructure, and retrieving, by the second host system, the socketinitialization request from the work queue structure via the endpoint.The method may further comprise establishing a socket communicationconnection between the first host system and the second host systembased on the socket initialization request. Moreover, the method maycomprise processing send and receive communications between the firsthost system and the second host system using the established socketcommunication connection.

In other illustrative embodiments, a computer program product comprisinga computer recordable medium having a computer readable program recordedthereon is provided. The computer readable program, when executed on acomputing device, causes the computing device to perform various ones,and combinations of, the operations outlined above with regard to themethod illustrative embodiment.

In yet another illustrative embodiment, a data processing system isprovided. The data processing system may comprise a first host system, asecond host system, and a communication fabric coupling the first hostsystem and the second host system. The data processing system mayperform various ones, and combinations of, the operations outlined abovewith regard to the method illustrative embodiment.

These and other features and advantages of the present invention will bedescribed in, or will become apparent to those of ordinary skill in theart in view of, the following detailed description of the exemplaryembodiments of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features believed characteristic of the invention are setforth in the appended claims. The invention itself, however, as well asa preferred mode of use, further objectives and advantages thereof, willbest be understood by reference to the following detailed description ofan illustrative embodiment when read in conjunction with theaccompanying drawings, wherein:

FIG. 1 is an exemplary diagram illustrating a PCIe fabric topology as isgenerally known in the art;

FIG. 2 is an exemplary diagram illustrating system virtualization as isgenerally known in the art;

FIG. 3 is an exemplary diagram illustrating a first approach tovirtualizing I/O of a PCI root complex using a I/O virtualizationintermediary;

FIG. 4 is an exemplary diagram illustrating a second approach tovirtualizing I/O of a PCI root complex using natively shared PCI I/Oadapters;

FIG. 5 is an exemplary diagram of a PCIe I/O virtualization enabledendpoint;

FIG. 6 is an exemplary diagram illustrating physical and virtualfunctions of single root endpoints without native virtualization;

FIG. 7 is an exemplary diagram illustrating physical and virtualfunctions of single root endpoints enabled for native I/Ovirtualization;

FIG. 8 is an exemplary diagram illustrating a multi-root virtualized I/Otopology in accordance with one illustrative embodiment;

FIG. 9 is an exemplary diagram illustrating a virtual hierarchy view ofa multi-root virtualized I/O topology from the viewpoint of a SR-PCIM ofa root node in accordance with one illustrative embodiment;

FIG. 10 is an exemplary diagram illustrating a shared memory PCIe basedsystem in accordance with one illustrative embodiment;

FIGS. 11A and 11B are diagrams representing exemplary virtual PCI treedata structures in accordance with one illustrative embodiment;

FIG. 12 is a flowchart outlining an exemplary operation for initializingmemory address spaces of host systems for sharing of endpoints inaccordance with one illustrative embodiment;

FIG. 13 is an exemplary block diagram illustrating a process for sendinga work queue element (WQE) from a first host system to a second hostsystem in accordance with one illustrative embodiment;

FIG. 14 is an exemplary block diagram illustrating a process for sendinga completion queue element (CQE) from the second host system to thefirst host system in accordance with one illustrative embodiment;

FIG. 15 is an exemplary flowchart outlining an exemplary operation fortransmitting a WQE between a root complex of a first host system and anendpoint associated with a second host system in accordance with oneillustrative embodiment;

FIG. 16 is an exemplary flowchart outlining an exemplary operation fortransmitting a CQE from an endpoint of a second host system to a rootcomplex of a first host system in accordance with one illustrativeembodiment;

FIG. 17 is an exemplary table illustrating the various possiblecombinations of transactions that may be used to perform communicationsbetween root complexes and endpoints of the same or different hostsystems;

FIG. 18 is an exemplary block diagram illustrating a process forestablishing sockets and performing socket-based communication between afirst host system to a second host system in accordance with oneillustrative embodiment;

FIG. 19 is a flowchart outlining an exemplary operation for performing apull transaction using a socket based communication connection inaccordance with one illustrative embodiment;

FIG. 20 is a flowchart outlining an exemplary operation for performing apush transaction using a socket based communication connection inaccordance with one illustrative embodiment;

FIGS. 21A and 21B are exemplary diagrams illustrating a single rootstateless migration of a virtual function and its associated applicationfrom one physical function to another on the same PCIe adapter inaccordance with one illustrative embodiment;

FIGS. 22A and 22B are exemplary diagrams illustrating a single rootstateless migration of a virtual function and its associated applicationfrom one PCIe adapter to another in accordance with one illustrativeembodiment;

FIGS. 23A and 23B are exemplary diagrams illustrating a single rootstateless migration of a virtual function and its associated applicationfrom one system image to another in accordance with one illustrativeembodiment;

FIG. 24 is a flowchart outlining an exemplary operation for migrating avirtual function in accordance with one illustrative embodiment;

FIG. 25 is an exemplary block diagram illustrating a hot-pluginoperation for a root complex in accordance with one illustrativeembodiment;

FIG. 26 is a flowchart outlining an exemplary operation for adding acomponent to a PCIe fabric in accordance with one illustrativeembodiment; and

FIG. 27 is a flowchart outlining an exemplary operation for dynamicallyremoving a component from a PCIe fabric in accordance with oneillustrative embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The illustrative embodiments provide a mechanism that allows a PCIeadaptor, or “endpoint,” to be natively shared by two or more systemimages (SIs) of the same or different root complexes, which may be onthe same or different root nodes, e.g., blades of a blade server.Further, the illustrative embodiments provide a mechanism by whichcommunication is facilitated between the system images and nativelyshared endpoints. In addition, the illustrative embodiments providemechanisms for migrating virtual functions between virtual planes, rootcomplexes, and system images to facilitate management of the PCIefabric. Moreover, the illustrative embodiments provide a mechanism bywhich a root complex's single root PCI manager (SR-PCIM) is able toread, from an endpoint, the valid combinations of functions that theendpoint implementer allowed when designing the endpoint. The SR-PCIMmay then set the combinations of functions that will be used in thecurrent configuration in which the endpoint is being used.

FIG. 2 is an exemplary diagram illustrating system virtualization as isgenerally known in the art. System virtualization is the division of aphysical system's processors, memory, I/O adapters, storage, and otherresources where each set of resources operates independently with itsown system image instance and applications. In such systemvirtualization, virtual resources are composed from physical resourcesand operate as proxies for physical resources, e.g., memory, diskdrives, and other hardware components with architectedinterfaces/functions, having the same external interfaces and functions.System virtualization typically utilizes a virtualization intermediarywhich creates virtual resources and maps them to the physical resourcesthereby providing isolation between virtual resources. Thevirtualization intermediary is typically provided as one of, or acombination of, software, firmware, and hardware mechanisms.

As shown in FIG. 2, typically in a virtualized system, an application210 communicates with a system image (SI) 220 which is a softwarecomponent, such as a general or special purpose operating system, withwhich specific virtual and physical resources are assigned. The systemimage 220 is associated with a virtual system 230 which is comprised ofthe physical or virtualized resources necessary to run a single SIinstance, e.g., virtualized processors, memory, I/O adapters, storage,etc.

The system image 220, via the use of the virtual system 230, accessesphysical system resources 250 by way of the virtualization intermediary240. The virtualization intermediary 240 manages the allocation ofresources to a SI and isolates resources assigned to a SI from access byother SIs. This allocation and isolation is often performed based on aresource mapping performed by the virtualization intermediary 240 andone or more resource mapping data structures maintained by thevirtualization intermediary 240.

Such virtualization may be used to allow virtualization of I/Ooperations and I/O resources. That is, with regard to I/O virtualization(IOV), a single physical I/O unit may be shared by more than one SIusing an I/O virtualization intermediary (IOVI), such as virtualizationintermediary 240. The IOVI may be software, firmware, or the like, thatis used to support IOV by intervening on, for example, one or more ofconfiguration, I/O, and memory operations from a SI, and direct memoryaccess (DMA), completion, and interrupt operations to a SI.

FIG. 3 is an exemplary diagram illustrating a first approach tovirtualizing I/O of a PCI root complex using an I/O virtualizationintermediary. As shown in FIG. 3, a host processor set 310, which may beone or more processors of a chip, motherboard, blade, or the like, maysupport a plurality of system images 320-330 through which applications(not shown) may access system resources, such as PCIe endpoints 370-390.The system images communicate with the virtualized resources via the I/Ovirtualization intermediary 340, PCIe root complex 350, and one or morePCIe switches 360, and/or other PCIe fabric elements.

With the approach illustrated in FIG. 3, the I/O virtualizationintermediary 340 is involved in all I/O transactions and performs allI/O virtualization functions. For example, the I/O virtualizationintermediary 340 multiplexes I/O requests from the various SIs' I/Oqueues onto a single queue in the PCIe endpoints 370-390. Thus, the I/Ovirtualization intermediary acts as a proxy between the SIs 320-330 andthe physical PCIe endpoints 370-390.

Such involvement by the I/O virtualization intermediary 340 mayintroduce additional delay in the I/O operations which limits the numberof I/O operations per unit of time, and thus limits I/O performance. Inaddition, the involvement of the I/O intermediary requires extra CPUcycles, thus reducing the CPU performance that is available to othersystem operations. Extra context switches and interrupt redirectionmechanisms required by this approach can also affect overall systemperformance. Furthermore, an IOVI 340 is not feasible when an endpoint370-390 is shared between multiple root complexes.

FIG. 4 is an exemplary diagram illustrating a second approach tovirtualizing I/O of a PCI root complex using natively shared PCI I/Oadapters. As shown in FIG. 4, a host processor set 410, which may be oneor more processors of a chip, motherboard, blade, or the like, maysupport a plurality of system images 420-430 through which applications(not shown) may access system resources, such as PCIe I/O virtualization(IOV) endpoints 470-490. The system images 420-430 communicate with thevirtualized resources via the PCIe root complex 440 and one or more PCIeswitches 460, and/or other PCIe fabric elements.

The PCIe root complex 440 includes root complex virtualization enablers(RCVE) 442 which may comprise one or more address translation andprotection table data structures, interrupt table data structures, andthe like, that facilitate the virtualization of I/O operations with IOVenabled endpoints 470-490. The address translation and protection tabledata structures may be used by the PCIe root complex 440 to performaddress translation between virtual and real addresses for virtualizedresources, control access to virtual resources based on a mapping ofvirtual resources to SIs, and other virtualization operations, forexample. These root complex interrupt table data structures areaccessible through the PCIe memory address space and are used to mapinterrupts to appropriate interrupt handlers associated with SIs, forexample.

As with the arrangement shown in FIG. 3, an I/O virtualization interface450 is provided in the virtualization structure of FIG. 4 as well. TheI/O virtualization interface 450 is used with non-IOV enabled PCIeendpoints that may be coupled to the PCIe switch 460. That is, the I/Ovirtualization interface (IOVI) 450 is utilized with PCIe endpoints in asimilar manner as described previously above with regard to FIG. 3 forthose PCIe endpoints that do not have native, i.e. internal to theendpoint, support for I/O virtualization (IOV).

For IOV enabled PCIe endpoints 470-490, the IOVI 450 is used primarilyfor configuration transaction purposes and is not involved in memoryaddress space operations, such as memory mapped input/output (MMIO)operations initiated from a SI or direct memory access (DMA) operationsinitiated from the PCIe endpoints 470-490. To the contrary, datatransfers between the SIs 420-430 and the endpoints 470-490 areperformed directly without intervention by the IOVI 450. Direct I/Ooperations between the SIs 420-430 and the endpoints 470-490 is madepossible by way of the RCVEs 442 and the built-in I/O virtualizationlogic, e.g., physical and virtual functions, of the IOV enabled PCIeendpoints 470-490, as will be described in greater detail hereafter. Theability to perform direct I/O operations greatly increases the speed atwhich I/O operations may be performed, but requires that the PCIeendpoints 470-490 support I/O virtualization.

FIG. 5 is an exemplary diagram of a PCIe I/O virtualization (IOV)enabled endpoint. As shown in FIG. 5, the PCIe IOV endpoint 500 includesa PCIe port 510 through which communications with PCIe switches, and thelike, of a PCIe fabric may be performed. Internal routing 520 providescommunication pathways to a configuration management function 530 and aplurality of virtual functions (VFs) 540-560. The configurationmanagement function 530 may be a physical function as opposed to thevirtual functions 540-560. A physical “function,” as the term is used inthe PCI specifications, is a set of logic that is represented by asingle configuration space. In other words, a physical “function” iscircuit logic that is configurable based on data stored in thefunction's associated configuration space in a memory, such as may beprovided in the non-separable resources 570, for example.

The configuration management function 530 may be used to configure thevirtual functions 540-560. The virtual functions are functions, withinan I/O virtualization enabled endpoint, that share one or more physicalendpoint resources, e.g. a link, and which may be provided in thesharable resource pool 580 of the PCIe IOV endpoint 500, for example,with another function. The virtual functions can, without run-timeintervention by an I/O virtualization intermediary, directly be a sinkfor I/O and memory operations from a system image, and be a source ofDirect Memory Access (DMA), completion, and interrupt operations to asystem image (SI).

PCIe endpoints may have many different types of configurations withregard to the “functions” supported by the PCIe endpoints. For example,endpoints may support a single physical function (PF), multipleindependent PFs, or even multiple dependent PFs. In endpoints thatsupport native I/O virtualization, each PF supported by the endpointsmay be associated with one or more virtual functions (VFs), whichthemselves may be dependent upon VFs associated with other PFs.Exemplary relationships between physical and virtual functions will beillustrated in FIGS. 6 and 7 hereafter.

FIG. 6 is an exemplary diagram illustrating physical and virtualfunctions of single root endpoints without native virtualization. Theterm “single root endpoints” refers to an endpoint that is associatedwith a single root complex of a single root node, i.e. a single hostsystem. With a single root endpoint, the endpoint may be shared by aplurality of system images (SIs) associated with a single root complex,but cannot be shared among a plurality of root complexes on the same ordifferent root nodes.

As shown in FIG. 6, the root node 600 includes a plurality of systemimages 610, 612, which communicate with PCIe endpoints 670-690, an I/Ovirtualization intermediary 630 (which is used as previously described),PCIe root complex 640, and one or more PCIe switches 650 and/or otherPCIe fabric elements. The root node 600 further includes a single rootPCIe configuration management (SR-PCIM) unit 620. The SR-PCIM unit 620is responsible for managing the PCIe fabric, which includes the rootcomplex 640, the one or more PCIe switches 650, and the like, and theendpoints 670-690. The management responsibilities of SR-PCIM 620include determination of which functions are to be assigned to which SIs610, 612 and the setup of the configuration space of the endpoints670-690. The SR-PCIM 620 may configure the functions of the variousendpoints 670-690 based on a SI's capabilities and input from a user,such as a system administrator, or load balancing software as to whichresources are to be assigned to which SIs 610, 612. A SI's capabilitiesmay include various factors including how much address space isavailable to allocate to the endpoint 670-690, how many interrupts areavailable to be assigned to the endpoint 670-690, and the like.

Each of the PCIe endpoints 670-690 may support one or more physicalfunctions (PFs). The one or more PFs may be independent of each other ormay be dependent upon each other in some fashion. A PF may be dependentupon another PF based on vendor defined function dependencies whereinone PF requires the operation of another PF or the result generated byanother PF, for example, in order to operate properly. In the depictedexample, PCIe endpoint 670 supports a single PF and PCIe endpoint 680supports a plurality of independent PFs, i.e. PF₀ to PF_(N), ofdifferent types 1 to M. A type relates to the functionality of the PF orVF, e.g., an Ethernet function and a Fiber Channel function are twodifferent types of functions. Endpoint 690 supports multiple PFs ofdifferent types with two or more of the PFs being dependent. In thedepicted example, PF₀ is dependent upon PF₁, or vice versa.

In the example shown in FIG. 6, the endpoints 670-690 are shared by thesystem images (SIs) 610 and 612 through the virtualization mechanismsmade available by the I/O virtualization intermediary (IOVI) 630. Asdescribed previously, in such an arrangement, the IOVI 630 is involvedin all PCIe transactions between the SIs 610, 612 and the PCIe endpoints670-690. The individual PCIe endpoints 670-690 need not supportvirtualization in themselves since the burden of handling thevirtualization is placed entirely on the IOVI 630. As a result, whileknown mechanisms for virtualization may be used in such an arrangement,the rate by which I/O operations may be performed is relatively slowcompared to the potential for I/O rates if the IOVI 630 were notinvolved in every I/O operation.

FIG. 7 is an exemplary diagram illustrating physical and virtualfunctions of single root endpoints enabled for native I/Ovirtualization. The arrangement shown in FIG. 7 is similar to that ofFIG. 6 with some important differences due to the PCIe endpoints 770-790supporting I/O virtualization (IOV) natively, i.e. within the endpointsthemselves. As a result, the I/O virtualization intermediary 630 in FIG.6 may be effectively eliminated, except of course for configurationoperations, with regard to the IOV enabled PCIe endpoints 770-790.However, if non-IOV enabled PCIe endpoints (not shown) are also utilizedin the arrangement, e.g., legacy endpoints, an I/O virtualizationintermediary may be used in conjunction with the elements shown in FIG.7 to handle sharing of such non-IOV enabled PCIe endpoints between thesystem images 710 and 712.

As shown in FIG. 7, the IOV enabled PCIe endpoints 770-790 may supportone or more independent or dependent physical functions (PFs) which inturn may be associated with one or more independent or dependent virtualfunctions (VFs). In this context, the PFs are used by the SR-PCIM 720 tomanage a set of VFs and are also used to manage endpoint functions, suchas physical errors and events. The configuration spaces associated withthe PFs define the capabilities of the VFs including the maximum numberof VFs associated with the PF, combinations of the PFs and VFs withother PFs and VFs, and the like.

The VFs are used by SIs to access resources, e.g., memory spaces,queues, interrupts, and the like, on the IOV enabled PCIe endpoints770-790. Thus, a different VF is generated for each SI 710, 712 which isgoing to share a specific PF. VFs are generated by the endpoint 770-790based on the setting of the number of VFs by the SR-PCIM 720 in theconfiguration space of the corresponding PF. In this way, the PF isvirtualized so that it may be shared by a plurality of SIs 710, 712.

As shown in FIG. 7, the VFs and PFs may be dependent upon other VFs andPFs. Typically, if a PF is a dependent PF, then all of the VFsassociated with that PF will also be dependent. Thus, for example, theVFs of the PF₀ may be dependent upon corresponding VFs of PF₁.

With the arrangement shown in FIG. 7, the SIs 710, 712 may communicatedirectly, via the PCI root complex 730 and PCIe switch 740, with the IOVenabled PCIe endpoints 770-790 and vice versa without the need forinvolvement by an I/O virtualization intermediary. Such directcommunication is made possible by virtue of the IOV support provided inthe endpoints 770-790 and in the SR-PCIM 720, which configures the PFsand VFs in the endpoints 770-790.

The direct communication between the SIs and the endpoints greatlyincreases the speed at which I/O operations may be performed between aplurality SIs 710, 712 and shared IOV enabled PCIe endpoints 770-790.However, in order for such performance enhancements to be made possible,the PCIe endpoints 770-790 must support I/O virtualization by providingmechanisms in the SR-PCIM 720 and the physical functions (PFs) of theendpoints 770-790 for generating and managing virtual functions (VFs).

The above illustrations of a PCIe hierarchy are limited to single roothierarchies. In other words, the PCIe endpoints are only shared by SIs710, 712 on a single root node 700 associated with a single PCI rootcomplex 730. The mechanisms described above do not provide support formultiple root complexes sharing the PCIe endpoints. Thus, multiple rootnodes cannot be provided with shared access to the resources of a PCIeendpoint. This limits the scalability of systems utilizing sucharrangements since a separate set of endpoints is required for each rootnode.

The illustrative embodiments herein make use of multi-root I/Ovirtualization in which multiple PCI root complexes may share access tothe same set of IOV enabled PCIe endpoints. As a result, the systemimages associated with each of these PCI root complexes may each shareaccess to the same set of IOV enabled PCIe endpoint resources but withthe protections of virtualization being in place for each SI on eachroot node. Thus, scalability is maximized by providing a mechanism forallowing addition of root nodes and corresponding PCI root complexeswhich may share the same existing set of IOV enabled PCIe endpoints.

FIG. 8 is an exemplary diagram illustrating a multi-root virtualized I/Otopology in accordance with one illustrative embodiment. As shown inFIG. 8, a plurality of root nodes 810 and 820 are provided with eachroot node having a single root PCI configuration manager (SR-PCIM) 812,822, one or more system images (SIs) 814, 816, 824, and 826, and a PCIroot complex 818 and 828. These root nodes 810 and 820, which may be,for example, blades in a blade server, are coupled to one or moremulti-root aware (MRA) PCIe switches 840 of a PCIe switch fabric whichmay include one or more such MRA PCIe switches 840, and/or other PCIefabric elements. The MRA switch 840 is of a different type than thenon-MRA switch 740 in FIG. 7 in that the MRA switch 840 has connectionsfor additional root nodes and contains the mechanisms required forkeeping the address spaces of those different root nodes separate anddistinct.

In addition to these root nodes 810 and 820, a third root node 830 isprovided that includes a multi-root PCI configuration manager (MR-PCIM)832 and corresponding PCI root complex 834. The MR-PCIM 832 isresponsible for discovering and configuring virtual hierarchies withinthe multi-root (MR) topology shown in FIG. 8, as will be discussed ingreater detail hereafter. Thus, the MR-PCIM 832 configures the physicaland virtual functions of the endpoints with regard to multiple rootcomplexes of multiple root nodes. The SR-PCIMs 812 and 822 configure thephysical and virtual functions of their associated single root complex.In other words, the MR-PCIM sees the MR topology as a whole, while theSR-PCIM sees only its own virtual hierarchy within the MR topology, asdescribed in greater detail hereafter.

As shown in FIG. 8, the IOV enabled PCIe endpoints 850 and 860 supportone or more virtual endpoints (VEs) 852, 854, 862, and 864. A VE is aset of physical and virtual functions assigned to a root complex. Thus,for example, a separate VE 852 and 862 are provided on the IOV enabledPCIe endpoints 850 and 860 for the PCI root complex 818 of root node810. Similarly, a separate VE 854 and 864 are provided on the IOVenabled PCIe endpoints 850 and 860 for the PCI root complex 828 of rootnode 820.

Each VE is assigned to a virtual hierarchy (VH) having a single rootcomplex as the root of the VH and the VE as a terminating node in thehierarchy. A VH is a fully functional PCIe hierarchy that is assigned toa root complex or SR-PCIM. It should be noted that all physicalfunctions (PFs) and virtual functions (VFs) in a VE are assigned to thesame VH.

Each IOV enabled PCIe endpoint 850 and 860 supports a base function (BF)859 and 869. The BF 859, 869 is a physical function used by the MR-PCIM832 to manage the VEs of the corresponding endpoint 850, 860. Forexample, the BF 859, 869 is responsible for assigning functions to theVEs of the corresponding endpoints 850, 860. The MR-PCIM 832 assignsfunctions to the VEs by using the fields in the BF's configuration spacethat allows assignment of a VH number to each of the PFs in the endpoint850, 860. In the illustrative embodiments, there can be only one BF perendpoint, although the present invention is not limited to such.

As shown in FIG. 8, each VE 852, 854, 862, and 864 may support their ownset of physical and virtual functions. As described previously, suchsets of functions may include independent physical functions, dependentphysical functions, and their associated independent/dependent virtualfunctions. As shown in FIG. 8, VE 852 supports a single physicalfunction (PF₀) with its associated virtual functions (VFs). VE 854likewise supports a single physical function (PF₀) with its associatedvirtual functions (VFs). VE 862 supports a plurality of independentphysical functions (PF₀-PF_(N)) and their associated virtual functions(VFs). VE 864, however, supports a plurality of dependent physicalfunctions (PF₀-PF_(N)).

A VE 852, 854, 862, or 864 may directly communicate with the SIs 814,816, 824, and 826 of the root nodes 810 and 820, if and only if the VEis assigned to a VH to which the SI has access, and vice versa. Theendpoints 850 and 860 themselves must support single root I/Ovirtualization, such as described previously above, and multi-root I/Ovirtualization as described with regard to the present illustrativeembodiments. This requirement is based on the fact that the topologysupports multiple root complexes but each individual root node sees onlyits associated single root based virtual hierarchy.

FIG. 9 is an exemplary diagram illustrating a virtual hierarchy view ofa multi-root virtualized I/O topology from the viewpoint of a rootcomplex of a root node in accordance with one illustrative embodiment.As shown in FIG. 9, while the multi-root (MR) topology may be as shownin FIG. 8, each root complex of each individual root node views only itsportion of the MR topology. Thus, for example, the PCI root complex 818associated with root node 810 sees its host processor set, its ownsystem images (SIs) 814, 816, the MRA switch 840, and its own virtualendpoints (VEs) 852 and 862. There is full PCIe functionality withinthis virtual hierarchy, however, the PCI root complex 818 does not seethe VEs, root complexes, system images, etc, that are not part of itsown virtual hierarchy.

Because of this arrangement, limitations are imposed on thecommunication between root complexes of root nodes in a MR topology.That is, since PCIe functionality is limited to the virtual hierarchyassociated with the root complex, root complexes cannot communicate withone another. Moreover, the system images associated with the variousroot complexes cannot communicate with system images of other rootcomplexes. In order to address such limitations, the illustrativeembodiments herein provide various mechanisms to provide support forcommunications between virtual hierarchies and specifically, rootcomplexes of different root nodes.

In order for a host system of the illustrative embodiments tocommunicate with multiple endpoints via its root complex, the hostsystem uses a shared memory that is shared by the various endpoints androot complexes with which the host system is associated. In order toensure proper operation of the endpoints with the host system, thisshared memory must be initialized such that each endpoint that isassociated with the host system is provided with its own portion of theshared memory through which various communications may be performed. Theillustrative embodiments utilize a mechanism for initializing the sharedmemory of a host system in which the PCIe fabric is discovered andendpoints of the PCIe fabric are virtually tied to root complexes of thehost systems. Each endpoint and root complex is then given its ownportion of a shared memory address space of each host system to which itis virtually tied. Through these portions of the host systems' sharedmemories, an endpoint associated with a root complex of one host systemmay communicate with one or more other root complexes of other hostsystems.

FIG. 10 is an exemplary diagram illustrating a shared memory PCIe basedsystem in accordance with one illustrative embodiment. As shown in FIG.10, a system 1000 has a host system 1010 that comprises a first rootcomplex (RC1) 1012 and a first endpoint (EP1) 1014, and is associatedwith a first multiple-root aware (MRA) switch 1016, which may also beprovided as part of the host system 1010. The system 1000 has a secondhost system 1020 that comprises a second root complex (RC2) 1022 and asecond endpoint (EP2) 1024, and is associated with a secondmultiple-root aware (MRA) switch 1026, which may also be provided aspart of the host system 1020. Each of these host systems 1010 and 1020may represent, for example, separate blades in a same multi-root bladecluster system 1000. Alternatively, the host systems 1010 and 1020 maybe provided on separate computing devices entirely. Each host system1010 and 1020 is in its own virtual hierarchy (VH). The host systems1010 and 1020 are connected to one another and with other sharedendpoints EP3-EP6 1042-1044 and 1052-054, via communication links withone or more MRA switches 1016, 1026, and 1032 of a PCIe fabric 1030. Thecommunication links associated with the host systems 1010 and 1020 andendpoints 1042-1044 and 1052-1054 may be associated with one or morevirtual planes (VPs).

There are no virtual hierarchy (VH) identifiers used in a PCIe fabric todistinguish which host system 1010 and 1020 is associated with a givenPCIe transaction. Instead a link local virtual plane (VP) identifier isused. Since the VP identifier is link local, RC 1's VH may have, forexample, VP=4 on a link between 1032 and 1016 and VP=4 on a link between1032 and 1042. In other words, a VH is made up of a set of PCIecomponents and the links that attach those components, with each ofthose links having a link local VP identifier used to designate which VHa given transaction is referencing.

In the depicted example, the goal is to permit the root complex 1012,and thus, the applications running in association with one or moresystem images associated with the root complex 1012, to communicate withan endpoint associated with another root complex, e.g., endpoint EP21024 associated with root complex RC2 1022. Thus, for example, EP2 1024may be used as an endpoint by system images running on root complex RC11012. In this way, endpoints that are co-resident with root complexesmay be shared across system images on various virtual planes and/or hostsystems. As a result, high performance node-to-node, i.e. host system tohost system, communications and load balancing may be facilitated aswell as system cost reduction by eliminating the need to go through anexternal networking adapter and switch, such as an InfiniBand orEthernet switch, when communicating between the nodes.

In order to permit endpoints to be shared by system images across hostsystems, a multi-root PCI configuration manager (MR-PCIM) 1062, providedin one of the host systems 1010 or 1020, or a separate host system 1060,initializes the host systems' memory spaces 1070 and 1080 to establishbase and limit apertures for the root complexes and endpoints. TheMR-PCIM 1062 accesses the PCIe fabric 1030 via the MRA switch 1064 andone or more MRA switches 1032 in the PCIe fabric 1030.

The MR-PCIM 1062 traverses the links of the PCIe fabric 1030 through thevarious interconnected switches, in a manner generally known in the art,to identify the root complexes and endpoints associated with the PCIefabric 1030. With the traversal performed by the illustrativeembodiments, however, all of the root complexes (RCs), with theexception of the root complex (RC) performing the discovery fabrictraversal operation, are treated as endpoints during the discoveryfabric traversal.

As the MR-PCIM 1062 traverses the PCIe fabric, it performs a number ofchecks between the root complexes and the endpoints to determine if agiven root complex is associated with a given endpoint. From theresulting information, the MR-PCIM 1062 generates one or more virtualPCI tree data structures that tie the endpoints available on the PCIefabric 1030 to each of the root complexes. Endpoints that are associatedwith the same root complex, are associated with each other in thevirtual PCI tree data structures.

After the MR-PCIM 1062 discovers and configures the fabric, therespective RCs allow their associated SR-PCIMs 1018 and 1028 to discoverand configure the VHs. Each SR-PCIM 1018, 1028 assigns, for each givenendpoint, a base address and limit within the PCIe memory addressspace(s) to which it belongs, e.g., the PCIe memory address space(s)associated with host system 1 memory 1070 and host system 2 memory 1080.The SR-PCIM 1018, 1028 writes this base address and limit to the BaseAddress Register (BAR) of the EP. Work requests and completion messagesmay then be written to these portions of the PCI memory address space(s)in order to facilitate communication between the various root complexesand the endpoints across host systems 1010 and 1020, as will bedescribed in greater detail hereafter.

As mentioned above, with the illustrative embodiments, the MR-PCIM 1062performs a number of checks between the root complexes and the endpointsas it traverses the PCIe fabric 1030. For example, the MR-PCIM 1062accesses the PCIe configuration space of each function, physicalfunction and virtual function of an EP, the PCIe configuration spacesbeing located in the EPs, as defined by the PCI specifications. TheMR-PCIM also accesses the Vital Product Data (VPD) fields for eachendpoint and stores the VPD information for later comparison, such as ina non-volatile storage area (not shown) coupled to the MR-PCIM 1062, forexample.

VPD is the information that uniquely defines items such as hardware,software, and microcode elements of a system. The VPD provides thesystem with information on various field replaceable units (FRUs)including vendor name, part number, serial number, and other detailedinformation that is useful for administration, asset management, andanything that requires unique identification of the PCI device. The VPDinformation typically resides in a storage device, e.g., a serialEEPROM, in a PCI device, such as an endpoint 1014, 1024. Moreinformation regarding VPD may be obtained from the PCI Local BusSpecification, Revision 3.0 available at www.pcisig.com.

The MR-PCIM 1062, after having retrieved and stored the VPD informationfor each of the endpoints 1014, 1024, 1042, 1044, 1052, and 1054,identifies which EP's and RC's reside on the same hardware device, e.g.blade. For example, the MR-PCIM 1062 accesses the VPD information of aMRA switch 1016, 1026, 1032 which contains a co-residency field thatindicates that it is associated with a hardware device which holds an RCand an EP. The MRA switch 1016, 1026, 1032 stores the VH assigned to theRC which may then be used to determine which EPs and RCs reside on thesame hardware device.

After determining that an EP co-exists with a RC on the same host, theMR-PCIM 1062 creates one or more virtual PCI tree data structures, suchas illustrated in FIGS. 11A and 11B. As shown in FIGS. 11A and 11B, thevirtual PCI tree data structure ties the endpoints available on the PCIefabric to each root complex.

It is assumed in the virtual PCI tree data structure shown in FIG. 11Athat the endpoints EP2 1024, EP4 1044, and EP5 1052 are associated withroot complex RC1 1012 via assignments indicated to the MR-PCIM 1062 bythe user. The VPD matching described above is only performed to allow aRC to determine that an EP is physically residing on the RC's host. Thistells the RC that the EP is accessible to the RC through standard PCImemory mapped addressing in the RC's address space. This is a physicalassociation. With the virtual PCI tree data structures, logicalassociations are specified by way of a user indicating that he/she wantsthe MR-PCIM 1062 to create such logical associations.

Similarly, it is assumed in FIG. 11B that the endpoints EP1 1014, EP31042, and EP6 1054 are associated with root complex RC1 1012 via userinput specifying logical associations, and their VPD information and thecomparisons made by the MR-PCIM 1062. Thus, in the depicted exampleshown in FIG. 11A, endpoint EP2 1024 is associated with, or tied with,root complex RC1 1012 via switch 2 1026 and switch 1 1016. Endpoints EP41044 and EP5 1052 are associated with root complex RC1 1012 via switch 31032 and switch 1 1016. In FIG. 11B, endpoint EP1 1014 is associatedwith, or tied with, root complex RC2 1022 via switch 1 1016 and switch 21026. Endpoints EP3 1042 and EP6 1054 are associated with root complexRC2 1022 via switch 3 1032.

Based on these virtual PCI tree data structures, the MR-PCIM 1062assigns each endpoint a base address and limit within the PCIe memoryaddress space(s) it belongs to. The base addresses may be stored in theendpoints' Base Address Registers (BARs). For example, EP1 1014 isaccessible through two PCIe memory address spaces 1070 and 1080. In hostsystem 1 1010, EP1 1014 is accessible by the host system's processor(not shown) through the host system's memory 1070 address space. In hostsystem 2 1020, EP1 1014 has a PCIe aperture, defined by the EP1 baseaddress and limit, in host system 2's memory 1080 address space that isaccessible via memory mapped I/O through PCI bus memory addresses. Theprocessor of host system 1 1010 may use a memory address translation andprotection table (not shown), such as may be provided in avirtualization intermediary, such as a hypervisor, the root complex1012, or the like, to map the PCIe memory addresses seen by theprocessor of host system 2 1020 into host system 1 memory addresses, forexample.

Similarly, the endpoint EP2 1024 is accessible through two PCIe memoryaddress spaces for host system memories 1070 and 1080. In host system 21020, EP2 1024 is accessible by host system 2's processor through hostsystem 2's real memory addresses for its memory 1080. In host system 11010, EP2 1024 has a PCIe aperture, defined by the base address andlimit for EP2 1024, in host system 1's memory 1070 that is accessible asmemory mapped I/O through PCI bus memory addresses. Host system 2 1020may use a memory address translation and protection table (not shown) tomap the PCIe memory addresses seen by host system 1 1010 into hostsystem 2 real memory addresses.

Similar portions of host system memories 1070 and 1080 may beinitialized for the root complexes RC1 1012 and RC2 1022. For example,in host system 1 1010, RC1 1012 is accessible by host system 1'sprocessor through host system 1's real memory addresses for host system1's memory 1070. RC1 1012 has a PCIe aperture in host system 2's memoryspace that is accessible via direct memory access (DMA) I/O through hostsystem 1's PCI bus memory addresses. Host system 1 1010 may use a memoryaddress translation and protection table (not shown) to map the PCIememory addresses seen by host system 2 1020 into host system 1 realmemory addresses.

Similarly, in host system 2 1020, RC2 1022 is accessible by host system2's processor through host system 2 real memory addresses for memory1080. RC2 1022 has a PCIe aperture in host system 1's memory 1070 thatis accessible as DMA I/O through host system 2's PCI bus memoryaddresses. Host system 2 1020 can use a memory address translation andprotection table (not shown) to map the PCIe memory addresses seen byhost system 1 1010 into host system 2 real memory addresses.

Thus, the mechanism of the illustrative embodiments provide for theinitialization of memory spaces in the host systems such that anendpoint may be accessible by more than one root complex in a pluralityof host systems. The portions of the memory spaces assigned to thevarious endpoints may then be utilized by the root complexes to sendrequests and completion messages to and from the endpoints.

FIG. 12 is a flowchart outlining an exemplary operation for initializingmemory address spaces of host systems for sharing of endpoints inaccordance with one illustrative embodiment. It will be understood thateach block of the flowchart illustration in FIG. 12, and flowchartillustrations described hereafter, and combinations of blocks in theflowchart illustrations, can be implemented by computer programinstructions. These computer program instructions may be provided to aprocessor or other programmable data processing apparatus to produce amachine, such that the instructions which execute on the processor orother programmable data processing apparatus create means forimplementing the functions specified in the flowchart block or blocks.These computer program instructions may also be stored in acomputer-readable memory or storage medium that can direct a processoror other programmable data processing apparatus to function in aparticular manner, such that the instructions stored in thecomputer-readable memory or storage medium produce an article ofmanufacture including instruction means which implement the functionsspecified in the flowchart block or blocks.

Accordingly, blocks of the flowchart illustrations support combinationsof means for performing the specified functions, combinations of stepsfor performing the specified functions and program instruction means forperforming the specified functions. It will also be understood that eachblock of the flowchart illustrations, and combinations of blocks in theflowchart illustrations, can be implemented by special purposehardware-based computer systems which perform the specified functions orsteps, or by combinations of special purpose hardware and computerinstructions.

As shown in FIG. 12, the operation starts with a MR-PCIM discovering thePCIe fabric by traversing all the links accessible throughinterconnected switches of the PCIe fabric (step 1210). VPD informationfor each of the endpoints and root complexes discovered during thediscovery of the PCIe fabric is stored (step 1220).

The MR-PCIM compares VPD information for each endpoint to the VPDinformation for each root complex to determine if a given endpoint isassociated with a given root complex (step 1230). For each comparison,the MR-PCIM sets a corresponding co-residency field if the VPDinformation matches for the endpoint and the root complex (step 1240).Based on the discovered endpoints and root complex information and thesettings of the co-residency fields for each of the comparisons, theMR-PCIM generates one or more virtual PCI tree data structures (step1250).

Based on the generated virtual PCI tree data structure(s), the MR-PCIMassigns to each endpoint a base address and limit within each PCIememory address space to which the endpoint belongs (step 1260). Based onthe generated virtual PCI tree data structure(s), the MR-PCIM assigns toeach root complex a base address and limit within each PCIe memoryaddress space to which that root complex belongs (step 1270). Theoperation then terminates.

Having initialized the memory address spaces of the host systems suchthat endpoints may be accessible by root complexes across host systems,these memory address spaces may then be used to allow system images, andtheir corresponding applications, associated with these root complexesto communicate with the endpoints. One way in which such communicationis facilitated is via a queuing system that utilizes these initializedmemory address spaces in the various host systems. Such a queuing systemmay comprise a work queue structure and a completion queue structure.Both the work queue structure and the completion queue structure maycomprise a doorbell structure for identifying a number of queue elements(either work queue elements (WQEs) or completion queue elements (CQE)depending upon whether the queue structure is a work queue structure ora completion queue structure), a base address for the start of a queue,a limit address for an end of the queue, and an offset which indicatesthe next WQE or CQE to be processed in the queue. Both the work queuestructure and the completion queue structure may be used to both sendand receive data.

FIG. 13 is an exemplary block diagram illustrating a process for sendinga work queue element (WQE) from a first host system to a second hostsystem in accordance with one illustrative embodiment. It is assumed,for purposes of this description, that a system is established havinghost systems, e.g., a first host system 1310 and a second host system1320, with multiple shared PCI root complexes, e.g., RC1 1312 and RC21322, connected by a PCIe fabric 1330, which may include MRA switches1316 and 1326 as well. It is further assumed that an endpoint, e.g., EP21324, residing in the second host system 1320 with root complex RC21322, is to be shared with a root complex RC1 1312 of a first hostsystem 1310 across the PCIe fabric 1330 and is appropriately mapped ontothe internal memory 1380 address space of the second host system 1320and the first host system's PCI bus memory address space. This systemconfiguration may be achieved, for example, by using the initializationmechanisms described previously with regard to FIGS. 10-12, for example.

As shown in FIG. 13, the endpoint EP1 1314 is accessible through memoryspaces associated with the two host system memories 1370 and 1380. On afirst host system 1310, the endpoint EP1 1314 is accessible by the firsthost system's processor through the first host system's real memoryaddresses for the first host system's memory 1370. On the second hostsystem 1320, the endpoint EP1 1314 has a PCIe aperture 1382 on thesecond host system's memory 1380 that is accessible as memory mapped I/Othrough PCI bus memory addresses. The first host system 1310 can use amemory address translation and protection table (ATPT) 1318 to map thePCIe memory addresses seen by the second host system 1320 into realmemory addresses for the first host system's memory space 1370.

Similarly, the endpoint EP2 1324 is accessible through the two hostsystem memory spaces 1370 and 1380. On the second host system 1320, theendpoint EP2 1324 is accessible by the second host system's processorthrough the second host system's real memory addresses and memoryaddress space 1380. On the first host system 1310, the endpoint EP2 1324has a PCIe aperture 1372 on the first host system's memory 1370 that isaccessible as memory mapped I/O through PCI bus memory addresses. Thesecond host system 1320 may use a memory address translation andprotection table (ATPT) 1328 to map the PCIe memory addresses sent bythe first host system 1310 to real memory addresses of the second hostsystem's memory space 1380.

A work queue structure 1374 may comprise a doorbell structure 1375 usedto pass a number of WQEs, a base address for the start of the queue, alimit address for the end of the queue, and an offset which indicatesthe next WQE to be processed in the work queue. Similarly, a completionqueue structure 1376 may comprise a doorbell structure 1377 used to passthe number of CQEs, a base address for the start of the queue, a limitaddress for the end of the queue, and an offset which indicates the nextCQE to be processed in the completion queue.

In order to send a WQE from the first host system 1310 to the secondhost system 1320, the first host system 1310 initiates the process byinserting one or more WQEs into its send work queue 1374. Each WQEcontains a list of data segments, where each data segment comprises abase address and a limit address that are both in the second hostsystem's PCIe memory bus address space and are also mapped, via anaddress translation and protection table (ATPT), to real memoryaddresses in the first host system's memory space 1370.

The first host system 1310 then writes the number of WQEs that are beingsent into endpoint EP2's PCIe address for the doorbell structure 1375.The address for this doorbell structure is mapped, via an ATPT, into thefirst host system's PCIe memory bus address space and is also mapped toreal memory addresses in the second host system's memory space 1380.When the doorbell write operation completes, the RC of the second hostsystem 1320 either polls, or gets an interrupt and then polls, toretrieve the doorbell structure 1375 through the first host system'sreal memory address space 1380. That is, the RC of the second hostsystem 1320 may be configured to periodically poll the address for thedoorbell structure 1375 to determine if new WQEs are to be processed.Alternatively, the setting of the doorbell structure 1375 by the firsthost system 1310 may generate an interrupt to the second host system1320 to inform the RC of the second host system 1320 of the new WQEsavailable for processing. The RC of the second host system 1320 may thenpoll the doorbell structure 1375 for the new WQEs' information andprocess them accordingly.

The endpoint EP2 1324 then performs PCIe DMA operations to root complexRC1 1312 to retrieve the WQEs. Each DMA operation uses the first hostsystem's PCIe memory bus address space and places the results of the DMAoperation into the second host system's memory 1380 that is accessibleon the second host system 1320 through its real memory address space.Thus, using the initialized shared memories of the host systems 1310 and1320, communication of work queue elements between root complexes andendpoints in different host systems 1310 and 1320 is facilitated.

FIG. 14 is an exemplary block diagram illustrating a process for sendinga completion queue element (CQE) from the second host system 1320 to thefirst host system 1310 in accordance with one illustrative embodiment.As shown in FIG. 14, once the work associated with a WQE, or group ofWQEs, is completed, the endpoint EP2 1324 performs one or more PCIe DMAoperations to root complex RC1 1312 to send one or more CQEs to the rootcomplex RC1 1312. The doorbell may be used in the sense that RC1 1312may poll or wait for an interrupt indicating a CQE is available.

Each DMA operation uses the first host system's PCIe memory bus addressspace and places the results into memory 1370 on the first host system1310 that is accessible on the first host system 1310 through its realmemory address space. The results are preferably stored in aDMA-addressable portion of memory 1370, the DMA-addressable portionbeing at different locations in memory 1370 depending upon theparticular OS utilized.

FIG. 15 is an exemplary flowchart outlining an exemplary operation fortransmitting a WQE between a root complex of a first host system and anendpoint associated with a second host system in accordance with oneillustrative embodiment. As shown in FIG. 15, the operation starts witha first host system inserting one or more WQEs into its send work queue(step 1510). The first host system then writes the number of WQEs thatare being sent into a target endpoint's PCIe address for a doorbellstructure (step 1520). When the doorbell write operation completes, asecond host system either polls, or gets an interrupt and then polls, toretrieve the doorbell structure through the first host system's realmemory address space (step 1530).

The target endpoint then performs PCIe DMA operations to the rootcomplex of the first host system to retrieve the WQEs (step 1540). Thetarget endpoint then places the results of the DMA operations into thesecond host system's memory (step 1550). The operation then terminates.

FIG. 16 is an exemplary flowchart outlining an exemplary operation fortransmitting a CQE from an endpoint of a second host system to a rootcomplex of a first host system in accordance with one illustrativeembodiment. The operation starts with an endpoint completing theprocessing work associated with one or more WQEs submitted to theendpoint (step 1610). The endpoint then performs one or more PCIe DMAoperations to a root complex associated with the host system from whichthe one or more WQEs were received to send one or more CQEs to the rootcomplex (step 1620). The results of the DMA operations are placed intothe first host system's memory (step 1630). The operation thenterminates.

Thus, the shared memories of the illustrative embodiments may be used toprovide a queuing structure through which work requests and completionmessages may be exchanged between root complexes and endpoints ondifferent host systems. Thus, a root complex may communicate withendpoints on host systems different from the host system on which theroot complex is provided, and vice versa.

In accordance with the illustrative embodiments herein, a transactionoriented protocol may be established for using the shared memories ofthe illustrative embodiments to communicate between root complexes andendpoints of the same or different host systems. The transactionoriented protocol specifies a series of transactions to be performed bythe various elements, e.g., root complex or endpoint, to push or pulldata, as will be described hereafter.

Returning to FIG. 13, the description above regarding the manner bywhich WQEs are provided to an endpoint and CQEs are returned to a rootcomplex is one example of a pull-pull-push protocol. That is, theendpoint EP2 1324 of the second host system 1320, in response to thewriting of the doorbell structure 1375 by the first host system 1310,uses PCIe DMA operations to pull the WQEs from the first host system'sshared memory 1370. These WQEs provide the “commands” for the operationsthat are to be performed. Based on the segment information stored in theWQEs, the endpoint EP2 1324 of the second host system 1320 pulls thecorresponding data from work queue structure 1374 in the first hostsystem's shared memory 1370. Once the work corresponding to the WQEs iscomplete, the endpoint EP2 1324 of the second host system 1320 pushes aCQE to the root complex RC1 1312 of the first host system 1310 using oneor more PCIe DMA operations. Thus, a pull-pull-push transaction protocolis utilized in the example of FIG. 13 described above.

Other possible combinations of the pull and push transactions arepossible for the establishment of different transaction protocols. FIG.17 is an exemplary table illustrating the various possible combinationsof transactions that may be used to perform communications between rootcomplexes and endpoints of the same or different host systems. As shownin FIG. 17, any combination of pull and push transactions may beutilized with the mechanisms of the illustrative embodiments to therebyestablish a transaction protocol for the use of the shared memories ofthe illustrative embodiments.

The root complex and the endpoints are responsible for enforcing aselected protocol. For example, the OS system stack and the endpointsperform the operations for pulling and pushing data as part of theselected transaction protocol, such as previously described. Theselection of a protocol to utilize is dependent on the particular PCIefabric utilized by the endpoints, e.g., InfiniBand or Ethernet fabric.The particularities of the protocol may be determined according to aprogramming choice, e.g., whether to use polling, interrupt processing,or a combination of polling and interrupt processing.

The mechanisms of the illustrative embodiments may further be used tosupport socket protocol based communication between root complexes andendpoints of the same or different host systems via the shared memoriesdescribed above. Such socket protocols may be used when a constantconnection is to be present. The determination as to whether to usesocket protocols or transaction-based protocols, such as the push-pulltransactions described above, may be made based on desired efficiencyand reliability.

With socket protocols, a work queue in the host systems may be used tolisten for incoming socket initialization requests. That is, a firsthost system that wishes to establish a socket communication connectionwith a second host system may generate a socket initialization requestWQE in its work queue and informs the second host system that the socketinitialization request WQE is available for processing. The second hostsystem may then accept or deny the request. If the second host systemaccepts the request, it returns the second half of the socket'sparameters for use by the first host system in performing socket basedcommunications between the first and second host systems. Suchcommunications may involve, for example, pull transactions and/or pushtransactions between the host systems.

FIG. 18 is an exemplary block diagram illustrating a process forestablishing sockets and performing socket-based communication between afirst host system and a second host system in accordance with oneillustrative embodiment. In a socket based implementation of theillustrative embodiments, endpoints, such as EP2 1824, on a host system,e.g., host system 1810, contain a receive buffer 1876, a buffer fullflag 1877, and a doorbell structure 1878. The buffer full flag 1877 andthe doorbell structure 1878 may comprise addresses in memory that serveto indicate that an event has happened. The transmitter host system,e.g., host system 1810, writes to the doorbell structure 1878 through aPCIe aperture 1872 in the memory 1870 of the receiver host system 1820accessible by the transmitter host system's root complex RC1 1812,corresponding to the connecting endpoint, e.g., endpoint EP2 1824.

As described previously, during initialization of the shared memories ofthe host system to facilitate the sharing of endpoints across aplurality of root complexes on the same or different host systems, vitalproduct data (VPD) information is read for each of the discovered rootcomplexes and endpoints in order to generate the virtual PCI tree datastructures. This VPD information may include a field indicating whetherthe particular root complex or endpoint supports sockets over PCIe. Thisinformation may be used to identify with which endpoints sockets may beestablished for socket-based communication in accordance with oneillustrative embodiment.

Thus, during initialization, the first host system 1810 may determinethat the endpoint EP2 1824 supports sockets over PCIe, for example,through a vendor specific field in the VPD for endpoint EP2 1824, theVPD information in the EP being accessible by the MR-PCIM as previouslydescribed above as well as by the host system itself. Similarly, thesecond host system 1820 may determine that the endpoint EP1 1814supports sockets over PCIe through its vendor specific field in the VPDinformation for endpoint EP1 1814.

Each host system 1810 and 1820 has a work queue (WQ) 1850 and 1860 thatit uses to listen for incoming sockets initialization requests. Forexample, the second host system 1820, i.e. the receiving host system,either blocks and waits for a socket initialization request to surfaceon its work queue 1860 or polls the doorbell structure 1878 of theendpoint EP2 1824 to determine if a socket initialization request hasarrived. The socket initialization request contains a base, limit, andstarting offset into the work queue 1850 to be used for the first hostsystem's half of the socket.

The first host system 1810, i.e. the sending host system, may generate asocket initialization request in its work queue 1850 and may write intothe endpoint EP2 1824 doorbell structure 1878 indicating a socketinitialization request WQE is available. Upon retrieving the data in thedoorbell structure 1878, the second host system's endpoint EP2 1824 mayperform a PCIe DMA operation to retrieve the socket initializationrequest from the first host system's work queue 1850 using the rootcomplex RC1's PCIe bus memory addresses which are accessible by theendpoint EP2 1824.

The second host system 1820 may then parse the socket initializationrequest and determine whether to accept or deny the socketinitialization request in an application or operating system specificmanner. If the second host system 1820 denies the socket initializationrequest, the second host system 1820 sends a non-connection responsePCIe DMA to the first host system's root complex RC1 1812 and, ifdesired, interrupts the first host system's root complex RC1 1812.

If the second host system 1820 accepts the socket initializationrequest, the endpoint EP2 1824 performs a PCIe DMA operation to thefirst host system's root complex RC1 1812 indicating the second half ofthe socket's parameters, i.e. the base, limit, and starting offset intothe work queue 1860 to be used for the second host system's half of thesocket.

Once the socket has been initialized in the manner described above,send/receive operations may be performed using the established socket inone of two ways: pull transactions or push transactions. With a pulltransaction, the root complex RC1 1812 of the first host system 1810performs send operations by writing a WQE to its work queue 1850 andthen writing to a doorbell structure 1878 associated with the endpointEP2 1824, which is accessible through root complex RC1 1812 PCIe busmemory address space. When the doorbell write operation completes, thesecond host system 1820 either polls or gets an interrupt and then pollsto retrieve the doorbell structure 1878 through the second host system'sreal memory address space. The endpoint EP2 1824 then performs a PCIeDMA operation to the root complex RC1 1812 to retrieve the WQEassociated with the send operation. The PCIe DMA operation uses thefirst host system's PCIe memory bus address space and places the resultsinto memory 1880 on the second host system that is accessible throughthe second host system's real memory address space. The second hostsystem 1820 then retrieves the data segment specified in the WQE andassociated with the send operation.

When the second host system completes the work requested in the WQE, theendpoint EP2 1824 performs a PCIe DMA operation to the root complex RC11812 to push a CQE signaling that the send operation has completed. ThisDMA operation uses the first host system's PCIe memory bus address spaceand places the results into memory 1870 on the first host system 1810that is accessible through the first host system's real memory addressspace.

For a push transaction, the root complex RC2 1822 writes into a doorbellstructure 1888 for endpoint EP1 1814 indicating the number of receiveWQEs it has available. When the endpoint EP1 1814 has data to send, theendpoint EP1 1814 checks to determine if the endpoint EP1 1814 has anyreceive WQEs available on the work queue 1860 of root complex RC2 1822.If there are no available receive WQEs, the root complex RC1 1812 writesinto the endpoint EP2's buffer full flag 1887 to indicate that the firsthost system 1810 has data to send on the socket and the second hostsystem 1820 needs to post some buffers through receive WQEs for thatsocket.

If there are available receive WQEs, the second endpoint EP2 1824performs a PCIe DMA operation to the root complex RC1 1812 to retrievethe next WQE available on the root complex RC1's work queue 1850. TheDMA operation uses the first host system's PCIe memory bus address spaceand places the results into memory 1880 on the second host system 1820that is accessible through the second host system's real memory addressspace. The second host system 1820 then sends its data to the datasegments passed in the receive WQE.

When the second host system 1820 completes the work requested, theendpoint EP2 1824 then performs a PCIe DMA operation to the root complexRC1 1812 to push a CQE signaling that the send operation has completed.This DMA operation uses the first host system's PCIe memory bus addressspace and places the results into memory on the first host system 1810that is accessible through the first host system's real memory addressspace.

FIG. 19 is a flowchart outlining an exemplary operation for performing apull transaction using a socket based communication connection inaccordance with one illustrative embodiment. The operation starts with aroot complex of a first host system writing a WQE to its work queue(step 1910) and then writing to a doorbell structure associated with atarget endpoint (step 1920). When the doorbell write operationcompletes, the second host system either polls or gets an interrupt andthen polls to retrieve the doorbell through the second host system'sreal memory address space (step 1930).

The target endpoint then performs a PCIe DMA operation to the rootcomplex of the first host system to retrieve the WQE associated with thesend operation (step 1940). The target endpoint places the results ofthe PCIe DMA operation into memory on the second host system (step1950). The second host system then retrieves the data segment specifiedin the WQE and associated with the send operation (step 1960).

In response to the second host system completing the work requested inthe WQE (step 1970), the target endpoint performs a PCIe DMA operationto the root complex of the first host system to push a CQE signalingthat the send operation has completed (step 1980). The root complex ofthe first host system places the results of the PCIe DMA operation intothe memory of the first host system (step 1990). The operation thenterminates.

FIG. 20 is a flowchart outlining an exemplary operation for performing apush transaction using a socket based communication connection inaccordance with one illustrative embodiment. A root complex of a secondhost system writes into a doorbell structure for an endpoint of a firsthost system, indicating the number of receive WQEs the root complex hasavailable (step 2010). In response to the endpoint of the first hostsystem having data to send (step 2020), the endpoint of the first hostsystem checks to determine if the endpoint has any receive WQEsavailable on the work queue of root complex of the second host system(step 2030). If there are no available receive WQEs, the root complex ofthe first host system writes into a second endpoint of the second hostsystem's buffer full flag to indicate that the first host system hasdata to send on the socket and the second host system needs to post somebuffers through receive WQEs for that socket (step 2040). The operationthen returns to step 2030)

If there are available receive WQEs, the second endpoint performs a PCIeDMA operation to the root complex of the first host system to retrievethe next WQE available on the root complex of the first host system'swork queue (step 2050). The second endpoint places the results of thePCIe DMA operation into the memory of the second host system (step2060). The second host system then sends its data to the data segmentspassed in the receive WQE (step 2070).

When the second host system completes the work requested, the secondendpoint performs a PCIe DMA operation to the root complex of the firsthost system to push a CQE signaling that the send operation hascompleted (step 2080). The second endpoint places the results of thePCIe DMA operation into memory on the first host system (step 2090). Theoperation then terminates.

As discussed above, the endpoints of a multi-root system may support oneor more physical functions having one or more associated virtualfunctions. The mechanisms of the illustrative embodiments, in additionto providing for the communication between root complexes and endpointsof the same or different host systems, also provides mechanisms formanaging the physical and virtual functions of an endpoint. One functionprovided by the mechanisms of the illustrative embodiments provides theability to migrate a single root stateless virtual function and itsassociated application from one physical function to another on the sameendpoint. This migration functionality is important to satisfying thegrowing demand for workload balancing capabilities in the realm ofsystem management.

By migrating the VF and its associated application(s) (which areapplications that depend on the VF to operate) different resources canbe recruited to continue operations in a more efficient environment. Forexample, with workload balancing, an Ethernet VF and its associateddependent application may be moved using the mechanisms of theillustrative embodiments to take advantage of a faster (e.g., lesscongested) connection available on a different PF that may be associatedwith a different SI or even EP altogether.

FIGS. 21A and 21B are exemplary diagrams illustrating a single rootstateless migration of a virtual function and its associated applicationfrom one physical function to another on the same endpoint, e.g., PCIeadapter, in accordance with one illustrative embodiment. As shown inFIG. 21A, an application 2110, associated with system image (SI) 2105,is associated with a virtual function (VF) 2120 as represented by thedashed line connecting element 2110 with 2120. A software intermediary2115, based on information from the SR-PCIM 2100, may depict migrationscenarios to the system administrator or equivalent administratingauthority. This may include, but is not limited to showing equivalentVFs that are available in the PCIe fabric that could be targets formigration via a systems management interface (not depicted).

The particular migration scenarios that may be depicted by SR-PCIM 2100may be determined, for example, based on a VF migration capability bitthat the SR-PCIM accesses to determine if a particular VF may bemigrated or not. Based on this information from the SR-PCIM 2100, theSWI 2115 may interpret and translate this data into VF migrationscenarios available to the user through a management console or entity.These migration scenarios will be highly dependent on the design of thecomponents in question. For example, in order to migrate an Ethernetadapter, an OS may have to be able to de-configure it. If thisfunctionality is not provided by the OS, then the management utilitywill not be able to depict such a scenario. In other words, themanagement utility maintains knowledge of the components (System Imagetype, Hardware, etc.) which it then uses to depict migration scenarios.This information, in addition with the migratability information storedin the VF migration capability bit, identifies which scenarios formigration are available for selection.

The system administrator starts the process to migrate a desired VF 2120and associated application 2110. For example, management software (notdepicted), may depict the VFs and their associated applications asentities, such as in a graphical user interface display, that can bemigrated between available resources on the host system and the PCIefabric. The management software can exist on a hardware managementconsole, such as the HMC available from International Business MachinesCorporation, or in any other console or part of the system runningsoftware designed to interact with firmware (e.g., softwareintermediaries or hypervisors), and control functions of the hardwareresources.

A software intermediary (SWI) 2115, which may be any type of firmware orsoftware code that is used between a management application and thehardware to create a layer of abstraction that allows for additionalfunctionality, running on the host system may send a request to the SI-A2105 that all outstanding requests be completed for or flexibility, theVF 2120 to be migrated. For example, the SI-A 2105 and the SWI 2115 mayhave application program interfaces (APIs) through which theycommunicate. The SI-A 2105 may respond to the request by pausing orstopping any application 2110 using the VF 2120. The SI-A 2105 mayensure that all outstanding requests to the VF 2120 are completed.Essentially, the SI-A 2105 checks to make sure that all queues are in astate that represents that no requests are pending and that alltransactions have been completed. For example, one way to do this is tocheck that all WQEs have a corresponding CQE.

The SI-A 2105 may then de-configure its logical representation of the VF2120, effectively stopping the SI-A's use of the VF 2120. This is anoperation that may be performed, for example, by a device driver (notshown) for the VF 2120 on the SI-A 2105. The SI-A 2105 may then notifythe SWI 2115 that all requests have been completed and that the VF 2120can be removed. The SWI 2115 may in turn remove the VF 2120 from theSI-A 2105. This will render the VF 2120 undetectable and un-configurableby the SI-A 2105. The SWI 2115 may now detach the VF 2120 from thetarget physical function (PF) 2135 by clearing out the VF'srepresentation in the configuration space of the endpoint.

Referring now to FIG. 21B, the SWI 2115 may then attach the target VF2145 to its PF 2140. The SWI 2115 may then make the VF 2145 available tothe SI-A 2105 for configuration and instructs the SI-A 2105 to configurethe VF 2145. For example, the SWI 2115 updates the SI-A's device tree infirmware to include a new device, e.g., the VF 2145 which may appear tobe a new endpoint, for example. This new endpoint, or VF 2145, may beany type of endpoint device whose logical representation in the OS isdependent on a device driver finding it in SI-A's device tree which ispresented to the OS by the firmware code. Once there is an entry inSI-A's device tree for the new device, e.g., the VF 2145, a devicedriver for that device will detect and configure the new device.

Once the SI-A 2105 configures the VF 2145 using, for example, a devicedriver, the associated application 2110 may then be able to use the VF2145. The SWI 2115 may now instruct the SI-A 2105 to start theassociated application 2110 completing the migration. As a result, theapplication 2110 and the VF 2120 are still associated, as represented bythe dashed line, but the VF 2120 has been migrated from its associationwith PF 2135 to now be associated with PF 2140.

FIGS. 22A and 22B are exemplary diagrams illustrating a single rootstateless migration of a virtual function (VF) and its associatedapplication from one endpoint, e.g., PCIe adapter, to another inaccordance with one illustrative embodiment. The operation for statelessmigration of a VF from one endpoint to another is similar to thatdescribed above with regard to FIGS. 21A and 21B. The main differencebetween the operation of FIGS. 21A-21B and that of FIGS. 22A-22B is thatthe VF is placed in a different endpoint altogether rather than onlybeing associated with a different physical function within the sameendpoint.

As shown in FIG. 22A, an application 2210, associated with system image(SI) 2205, is associated with a virtual function (VF) 2220 asrepresented by the dotted line connecting element 2210 with 2220. ASR-PCIM 2200 depicts migration scenarios to the system administrator orequivalent administrating authority. This may include, but is notlimited to showing equivalent VFs that are available in the PCIe fabricthat could be targets for migration via a systems management interface(not depicted).

The system administrator starts the process to migrate the desired VF2220 and associated application 2210. For example, management software(not depicted) may illustrate the VFs and their associated applicationsas entities, such as in a graphical user interface display of amanagement console or entity, that can be migrated between availableresources on the host system and the PCIe fabric. A softwareintermediary (SWI) 2215 running on the host system may send a request tothe SI-A 2205 that all outstanding requests be completed for the VF 2220to be migrated. For example, the SI-A 2205 and the SWI 2215 may haveapplication program interfaces (APIs) through which they communicate.The SI-A 2205 may respond to the request by pausing or stopping anyapplication 2210 using the VF 2220. The SI-A 2205 may ensure that alloutstanding requests to the VF 2220 are completed.

The SI-A 2205 may then de-configure its logical representation of the VF2220, effectively stopping the SI-A's use of the VF 2220. This is anoperation that may be performed, for example, by a device driver (notshown) for the VF 2220 on the SI-A 2205. The SI-A 2205 may then notifythe SWI 2215 that all requests have been completed and that the VF 2220can be removed. The SWI 2215 may in turn remove the VF 2220 from theSI-A 2205. This will render the VF 2220 undetectable and un-configurableby the SI-A 2205. The SWI 2215 may now detach the VF 2220 from thetarget physical function (PF) 2235 by clearing out the VF'srepresentation in the configuration space of the endpoint.

Referring now to FIG. 22B, the SWI 2215 may then attach the target VF2245 to its PF 2240 which is in a different endpoint altogether from thePF 2235 with which the VF 2220 (now VF 2245) was originally associated.The SWI 2215 may then make the VF 2245 available to the SI-A 2205 forconfiguration and instructs the SI-A 2205 to configure the VF 2245. Forexample, the SWI 2215 updates the SI-A's device tree in firmware toinclude the new device. The SI-A 2205 may configure the VF 2245 using,for example, a device driver whose type will depend on the specificproperties of the device or function in question. The associatedapplication 2210 may now be able to use the VF 2245. The SWI 2215 maynow instruct the SI-A 2205 to start the associated application 2210completing the migration. As a result, the application 2210 and the VF2220 are still associated, as represented by the dashed line, but the VF2220 has been migrated from its association with PF 2235 to now beassociated with PF 2240 in a different endpoint.

Similar operations may be performed to migrate a virtual function fromone system image to another. FIGS. 23A and 23B are exemplary diagramsillustrating a single root stateless migration of a virtual function andits associated application from one system image to another inaccordance with one illustrative embodiment. As shown in FIG. 23A, theoperation for stopping operations targeting a VF 2320 that is to bemigrated is essentially the same as described previously with regard toFIGS. 21A and 22A. Once the application 2310 associated with the VF 2320is stopped and operations targeting the VF 2320 are completed, the SI-A2305 de-configures its logical representation of the VF 2320 andnotifies the SWI 2315 that all requests have been completed and the VF2320 may be removed.

If a SI change is to be performed with regard to the VF 2320, the SWI2315 detaches the VF 2320 from the associated PF 2335 and attaches theVF 2345 to a target PF 2340. The target PF 2340 may be located on thesame or different endpoint. The SWI 2315 makes the VF 2345 available tothe target SI, e.g., SI-B 2350 for configuration and instructs thetarget SI 2350 to configure the VF 2345. The target SI 2350 configuresthe VF 2345 effectively making it available for use by the associatedapplication 2310, now associated with SI-B 2350. The SWI 2315 informsthe target SI 2350 to start the associated application to use theresources on the new VF 2345.

FIG. 24 is a flowchart outlining an exemplary operation for migrating avirtual function in accordance with one illustrative embodiment. Asshown in FIG. 24, the operation starts with a user specifying a VF tomigrate and a target destination for the VF (step 2410). A SWI runningon the host system sends a request to the SI that all outstandingrequests to the VF be completed in order to migrate the VF (step 2420).The SI pauses or stops any application using the VF (step 2430) andensures that all outstanding requests to the VF have completed (step2440). The SI then de-configures its logical representation of the VF(step 2450). The SI notifies the SWI that all requests have beencompleted and that the VF can be removed (step 2460).

The SWI then removes the VF from the SI and detaches the VF from theassociated PF (step 2470). The SWI then attaches the VF to the target PFwhich may be in the same or different endpoint and may be associatedwith the same or a different system image (step 2480). The SWI theninstructs the SI with which the VF is now associated to configure theVF, thereby making it available for use by an associated application(step 2490). The SWI instructs the SI to start the associatedapplication to use the resources on the new VF (step 2495). Theoperation then terminates.

Thus, with the mechanisms of the illustrative embodiments, virtualfunctions may be migrated within the same endpoint, between differentendpoints, and between different system images on the same or differentendpoints. Such migration makes it possible for various load balancingoperations to be performed. Moreover, such migration allows virtualfunctions to be moved to operating environments that are more conduciveto efficient operation of the virtual functions.

Thus, the illustrative embodiments as outlined provide mechanisms forsimultaneously sharing an endpoint, e.g., a PCIe I/O adapter, betweenmultiple system images (Sis) within the same root complex or acrossmultiple root complexes (RCs). Moreover, the mechanisms of theillustrative embodiments support the ability to use queue basedcommunication, push-pull based protocol communication, and socket basedcommunication. Furthermore, the illustrative embodiments providemechanisms for migrating virtual functions and their associatedapplication instances from one physical function to another in the sameor different endpoint and from one system image to another.

In addition to these mechanisms, the illustrative embodiments furtherprovide functionality for performing hot-plug/remove of a new componentinto a running multi-root PCIe fabric. These mechanisms allow a rootcomplex, for example, to be hot-plugged into or removed from a runningPCIe fabric. For example, a blade may be hot-plugged into a bladechassis and its associated root complex may be incorporated in real-timeinto the PCIe fabric in an existing system.

Such hot-plug/remove capability allows the PCIe fabric to grow and forvirtual functions to be natively shared across the newly incorporatedroot complexes. The PCIe fabric may thus expand without bringing downthe system in order to do so. The PCI-SIG I/O virtualization standardsdo not provide any such capability or standard for such dynamicexpansion of the PCIe fabric.

With the mechanisms of the illustrative embodiments, it is assumed thatthere is an existing host system with one or more PCI root complexes andmultiple-root aware (MRA) enabled switches. For example, the host systemmay have two root complexes RC1 and RC2 connected by a PCI fabric havingone or more MRA switches. Moreover, it is assumed that there are one ormore endpoints coupled to the PCIe fabric which may be configured tocommunicate with the existing root complexes and with the newlyintroduced root complex. Furthermore, it is assumed that a multiple root(MR) PCI configuration manager (MR-PCIM), which may reside in-band onone of the host systems or out-of-band, is capable of and has discoveredthe PCI fabric by traversing all of the links accessible throughinterconnected switches of the PCIe fabric. All of these assumptions aresatisfied by the various mechanisms previously described above withregard to the illustrative embodiments set forth herein.

With the above assumed configuration, when a system administrator, orthe like, adds a new root complex to an existing PCIe fabric (e.g.,inserts a new blade into a blade chassis), at least one of an automatedmechanism, such as a hot-plug controller, or the system administrator,notifies the MR-PCIM, such as via an administrator interface or thelike, of the addition of the root complex. Such notification may bemade, for example, by posting an event to the MR-PCIM indicating thatthe action of adding a new entity into the fabric has taken place. Suchan event may identify a switch and switch port where the new rootcomplex is now connected to the PCIe fabric, i.e. where the root complexis plugged-in.

The MR-PCIM may then handle the posted event by performing a number ofoperations to initialize the new root complex in the existing PCIefabric. For example, the MR-PCIM may update its PCIe fabricconfiguration data structure with information regarding the newly addedcomponent. The PCIe fabric configuration data structure is used by theMR-PCIM to represent the configuration of the PCIe fabric. Informationstored in the PCIe fabric configuration data structure is gathered bythe MR-PCIM from PCIe fabric configuration registers and from input froma system administrator, via a management user interface with theMR-PCIM, for example. The content of the PCIe fabric configuration datastructure and usage of this content will be described more fully,hereafter.

After updating the PCIe fabric configuration data structure, the MR-PCIMthen performs PCI configuration space operations, as defined by the PCIspecifications, to determine the characteristics of the newly addedcomponent, e.g., whether it is an endpoint, a root complex, a switch,etc., what type of endpoint, root complex, switch, etc. it is, and thelike, as per the PCI specifications. If it is determined that the newlyadded component is a switch, the PCI configuration space operations areperformed with regard to each port of the switch to determine theexistence of additional components coupled to the switch. Thecharacteristic information, e.g., component type, vendor name, partnumber, serial number, etc., for the newly added component is thenstored in the virtual PCIe fabric configuration data structure for useby the MR-PCIM.

If the component is a new root complex or a new endpoint, the MR-PCIMassociates the new root complex or endpoint with a virtual plane. Inthis way, the new root complex or endpoint is made available for use bythe system. If the component is a MRA switch, the MR-PCIM configures theswitch's virtual plane table, as per the PCI I/O virtualizationspecifications. If the component is a switch, then the switch ports arechecked to see what components, if any, are attached to them and theMR-PCIM configures its PCIe fabric configuration data structure based oninformation about these components as well in a similar manner. In thisway, the new component(s) may be dynamically added to the PCIe fabric.

With regard to a new root complex, having configured the MR-PCIM toinclude the characteristic information for the new root complex andassociated the new root complex with a virtual plane, the new rootcomplex may be used in the PCIe fabric. Thus, the mechanisms of theillustrative embodiments allow root complexes and their associatedcomponents to be added to an existing running PCIe fabric. As a result,there is no downtime for the system when expanding the system to includeadditional components.

FIG. 25 is an exemplary block diagram illustrating a hot-pluginoperation for a root complex in accordance with one illustrativeembodiment. It should be appreciated that while FIG. 25 shows thehot-plugin operation for a root complex, the illustrative embodimentsare not limited to such. Rather, as discussed above, the hot-plugoperation may be performed with regard to endpoints, switches, and othertypes of components without departing from the spirit and scope of thepresent invention.

As shown in FIG. 25, host system 2510 has existing root complexes RC12512 and RC2 2514 associated with virtual planes 2511 and 2513,respectively. The existing root complexes RC1 2512 and RC2 2514 areconfigured by the MR-PCIM 2562 to communicate with endpoints 2542, 2544,2552, and 2554 in virtual planes 2540 and 2550. The MR-PCIM 2562maintains a fabric configuration data structure 2566 which storescharacteristic information for all of the components of the PCIe fabric2530 and components attached to the PCIe fabric 2530, including thecomponents of host system 2510.

In the depicted example, it is assumed that a new root complex RC N 2516has been added to the host system 2510. For example, the root complex RCN 2516 may be associated with a blade and the host system 2510 may be ablade server having a chassis in which the blade associated with RC N2516 may be inserted. Other types of devices that may supply RC N 2516may be used without departing from the spirit and scope of theillustrative embodiments.

With the illustrative embodiments, there are two types of standard PCIhot-plug controllers associated with each switch port that is going toallow hot-plug/remove of components. One of these hot-plug controllersis used by the MR-PCIM 2562 for the physical aspects of thehot-plug/remove operations, and is referred to as the “physicalhot-plug” controller. There is one of these physical hot-plugcontrollers for each hot-pluggable port.

In addition, a “virtual hot-plug” controller is provided for the rootcomplexes which use the virtual hot-plug controller to control theirlogical connections to a shared component below a switch port. There isone virtual hot-plug controller per virtual plane supported by a switchport.

With the illustrative embodiments, in response to the addition of thenew RC N 2516, the physical hot-plug controller at the switch 2532 portassociated with RC N 2516 sends a “Presence Detect Change” interruptmessage to the MR-PCIM 2562 to inform the MR-PCIM 2562 that a newcomponent has been added to the PCIe fabric. This interrupt message isdefined by the PCI specifications, but the usage here is to direct theinterrupt to the MR-PCIM 2562 rather than to a root complex that doesnot run the MR-PCIM 2562. Alternatively, a system administrator may havealso informed the MR-PCIM 2562 via a management interface (not shown) tothe MR-PCIM 2562, prior to the insertion, as another form ofnotification of the addition of a new component.

The MR-PCIM 2562 may then handle the “Presence Detect Change” interruptby performing a number of operations to initialize the new component,e.g., root complex RC N 2516, in the existing PCIe fabric 2530. Forexample, the MR-PCIM 2562 updates its fabric configuration datastructure 2566 with information regarding the newly added component. Inupdating the fabric configuration data structure 2566, the MR-PCIM 2562performs PCI configuration space operations to query and determine thecharacteristics of the newly added component, e.g., whether it is anendpoint, a root complex, a switch, etc., what type of endpoint, rootcomplex, switch, etc. it is, vendor name, part number, serial number,and the like.

In addition to this automated query, when the added component is a rootcomplex, the system administrator may tell the MR-PCIM 2562, such asthrough a management interface (not shown) to the MR-PCIM 2562, whichcomponents to configure to the newly added root complex. For example,MR-PCIM 2562 needs to know which endpoints the system administratorwants to assign to the new RC N 2516 so that those endpoints can beadded to the correct virtual plane in order for the new RC N 2516 tohave access to them. This assignment of endpoints to a virtual plane isdone by the MR-PCI 2562 accessing PCI multi-root configurationstructures in PCI configuration spaces of the MRA switch 2532 and, ifthe endpoints are MRA endpoints, in the endpoints, in addition to theMRA switch 2532.

In the depicted example, the new component that was added is a rootcomplex RC N 2516, e.g., a blade providing RC N 2516. However, thecomponent may be any of a number of different types of components andthus, the MR-PCIM 2562 may determine the type of component being addedbased on the characteristics information gathered from the addedcomponent. Based on the determined type of component that is beingadded, various operations may be performed by the MR-PCIM 2562 todynamically add the component to the PCIe fabric 2530 such that it maybe employed in communications and operations of the PCIe fabric 2530.

Since, in the depicted example, the added component is a new rootcomplex RC N 2516, the MR-PCIM 2562 associates the new root complex RC N2516 with a virtual plane 2515 and then associates the endpoints thatthe system administrator has specified to the new root complex RC N2516, as detailed previously. In this way, the new component may bedynamically added to the PCIe fabric.

With the new root complex RC N 2516 having been added to the PCIe fabric2530 by the MR-PCIM 2562, by including the characteristic informationfor the new root complex RC N 2516 in the fabric configuration datastructure 2566, setting up the PCI configuration spaces of thecomponents to be associated with the new root complex, and associatingthe new root complex with a virtual plane 2515, the new root complex RCN 2516 may be used in the PCIe fabric 2530. The above operation isperformed dynamically while the PCIe fabric 2530 continues to function.Thus, the illustrative embodiments provide a mechanism for hot-plugginga component into a running PCIe fabric 2530.

It should be noted that the fabric configuration data structure 2566,which is kept current with the system configuration by the MR-PCIM 2562,can be used for a number of purposes. For example, it can be used todisplay to the system administrator, via the MR-PCIM's managementinterface, the I/O configuration of the PCIe fabric 2530. That is, arepresentation of which endpoints are assigned to which root complexes,which endpoints have not been assigned to any root complexes and thusare available to be assigned, and the like, may be provided to thesystem administrator via a management interface provided by the MR-PCIM2652. The fabric configuration data structure 2566 may also be persistedacross system power cycles in a non-volatile storage, such as flashmemory or hard disk, so that when the system powers on, the previousassignments of endpoints to root complexes, as previously assigned bythe system administrator, may be restored automatically by the MR-PCIM2562.

The fabric configuration data structure 2566 is maintained with all theknown information obtained from the I/O communication fabric 2530, theendpoint PCI configuration registers, and the information input by thesystem administrator via the management interface of the MR-PCIM 2562.The fabric configuration data structure 2566 identifies the treestructure of the I/O structure, and hence can be used to know whichcomponents will be removed when a removal operation is performed, asdescribed below.

In the above example, a root complex was added. When this happens, theroot complex's firmware and software, as part of the normal power-upoperation, will probe the I/O configuration information in the fabricconfiguration data structure 2566 using normal PCI configurationaccesses. When an endpoint is the component being added to a running I/Ocommunication fabric 2530, once the system administrator has added thecomponent to the desired root complex through the MR-PCIM's managementinterface, the MR-PCIM 2562, after configuring the endpoint to thedesired virtual plane as described above, then signals the root complexthat the endpoint has been added via the virtual hot-plug controller,previously mentioned. The root complex, as a result, receives aninterrupt from the virtual hot-plug controller and initiates thesoftware that will configure and start to use the new endpoint. Hence,an endpoint can be added without stopping the current system operations.

In addition, the mechanisms of the illustrative embodiments also providefunctionality for dynamically removing components from the PCIe fabric2530. Similar to the “Add” event, the MR-PCIM 2562 may be notified of a“Remove” event by a system administrator via an interface, automaticdetection mechanism, or the like. With a “Remove” event, the eventidentifies to the MR-PCIM 2562 in which virtual tree branch of thevirtual hierarchies, managed by the MR-PCIM 2562, the removal operation(i.e. the hot-plug removal of the component), has occurred or willoccur.

In a removal operation, the components which are to be removed areidentified by the fabric configuration data structure 2566. As mentionedpreviously, this fabric configuration data structure 2566 identifies atree structure of the I/O components. The removal operation points tothe component in the tree structure that is to be removed, andeverything below that component will also be removed. For example, thecomponent to be removed might be pointed to by a graphical managementinterface displayed to the system administrator via the MR-PCIM 2562management interface. In which case, the MR-PCIM 2562 knows how thatselected component is related to other components via the fabricconfiguration data structure 2566.

Alternatively, the relationships of the component may be identified bythe status bits in a virtual hot-plug controller associated with thecomponent. In this latter case, the virtual hot-plug controller mayissue an interrupt message to the MR-PCIM 2562 which may then read thestatus from the virtual hot-plug controller's registers to see whichcomponents were to be removed. In such a case, the MR-PCIM 2562 may scanthe fabric configuration data structure 2566 to find the component, inorder to discover which components need to be removed.

Examples of a remove operation include the operation to remove endpointEP5 2552, in which case, only that endpoint would be identified forremoval based on the tree structure in the fabric configuration datastructure 2566. As another example, the removal of MRA switch 3 2532,would involve the removal of MRA switch 3 2532 and endpoints EP3-EP62542-2554, based on tree structure of the fabric configuration datastructure 2566.

The MR-PCIM 2562 handles the “Remove” event by updating its virtual PCIefabric configuration data structure 2566 to remove the componentassociated with the “Remove” event and updating the PCI configurationspaces of the components in the tree branch or branches involved toremove them from the virtual plane that they previously occupied. Afterremoval, endpoints may be returned to an unused component pool, and maybe assigned later, by the system administrator, to another root complex.Specifically, if the component is an endpoint, as identified by the PCIconfiguration information in the fabric configuration data structure2566, the MR-PCIM 2562 removes the endpoint from the virtual plane inthe virtual tree hierarchy it was in. If the component is, or provides,a root complex, the virtual plane associated with the component isremoved from all components that were part of that virtual plane. Thus,in addition to being able to dynamically add components to a PCIefabric, the mechanisms of the illustrative embodiments further providethe ability to dynamically remove components from the PCIe fabric whilethe PCIe fabric is operating or running.

FIG. 26 is a flowchart outlining an exemplary operation for adding acomponent to a PCIe fabric in accordance with one illustrativeembodiment. As shown in FIG. 26, the operation starts by receiving, in aMR-PCIM, an “Add” event indicating the addition of a component to thePCIe fabric (step 2610). As discussed above, this event may identify theswitch and switch port to which the component is added and may begenerated in response to an automatic detection of the addition of thecomponent or in response to a system administrator command input, forexample. The “Add” event may be received as part of a “Presence DetectChange” interrupt sent by a physical hot-plug controller of a PCIeswitch in response to the detection of the addition of the newcomponent, for example.

The MR-PCIM gathers characteristic information for the added component(step 2620). This gathering may comprise communicating with thecomponent to retrieve the characteristic information, such as from a VPDstorage device associated with the component or the like. Moreover, thegathering may comprise the MR-PCIM performing PCI configuration spaceoperations to determine these characteristics of the newly addedcomponent. The MR-PCIM determines, based on the gathered characteristicinformation, if the component is a switch (step 2630). If the componentis a switch, then the MR-PCIM gathers characteristic information for anycomponents attached to the switch's ports (step 2640). The MR-PCIMdetermines, based on the characteristic information for the component,if the switch is a MRA switch or a base switch (step 2650). If theswitch is a MRA switch, the MR-PCIM configures the MRA switches virtualplane table (step 2660). If the switch is a base switch, the MR-PCIMassigns all ports on the switch to one virtual plane (step 2670).

If the component is not a switch, then the MR-PCIM determines that thecomponent provides a new root complex or endpoint. The MR-PCIMassociates the root complex or endpoint with a virtual plane (step2680). The characteristic information for the component is then used toupdate the PCIe fabric configuration data structure associated with theMR-PCIM based on the associated virtual plane(s) (step 2690). Thisupdating may comprise, for example, updating one or more virtualhierarchies maintained in the fabric configuration data structure.Finally, the MR-PCIM updates the PCI configuration space VP identifiers(step 2695). The operation then terminates.

FIG. 27 is a flowchart outlining an exemplary operation for dynamicallyremoving a component from a PCIe fabric in accordance with oneillustrative embodiment. As shown in FIG. 27, the operation starts withthe MR-PCIM receiving a “Removal” event (step 2710). As discussed above,this event may be generated in response to an automatic detection of theremoval of the component or in response to a system administratorcommand input, for example.

The MR-PCIM determines if the component that is being removed is anendpoint (step 2720). If the component is an endpoint, then thecomponent is removed from the virtual plane to which it was assigned inthe PCIe fabric configuration data structure associated with the MR-PCIM(step 2730). If the component is not an endpoint, then the component isa root complex. If the component is a root complex, the MR-PCIM removesthe virtual plane associated with the root complex from all componentsthat were part of that virtual plane in the PCIe fabric configurationdata structure (step 2740). In addition to the component being removedfrom the MR-PCIM's fabric configuration data structure, MR-PCIM alsoissues PCI configuration operations to the affected components to updatethe VP numbers in the components (step 2750). The operation thenterminates.

Thus, the mechanisms of the illustrative embodiments provide variousfunctionalities for sharing endpoints across multiple system images androot complexes. These functionalities include the configuring of sharedmemory spaces for use in communicating between root complexes andendpoints, dynamically adding or removing root complexes and othercomponents, and the like. These various mechanisms all add to a system'sability to expand as requirements change over time. Moreover, thesevarious mechanisms enhance workload balancing, concurrent maintenance,and a plethora of other desired system capabilities.

It is important to note that while the present invention has beendescribed in the context of a fully functioning data processing system,those of ordinary skill in the art will appreciate that the processes ofthe present invention are capable of being distributed in the form of acomputer readable medium of instructions and a variety of forms and thatthe present invention applies equally regardless of the particular typeof signal bearing media actually used to carry out the distribution.Examples of computer readable media include recordable-type media, suchas a floppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs, andtransmission-type media, such as digital and analog communicationslinks, wired or wireless communications links using transmission forms,such as, for example, radio frequency and light wave transmissions. Thecomputer readable media may take the form of coded formats that aredecoded for actual use in a particular data processing system.

The description of the present invention has been presented for purposesof illustration and description, and is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain theprinciples of the invention, the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

1. A method, in a data processing system, for communicating between afirst host system and a second host system, comprising: initializing amemory address space in a shared memory of the first host system tocomprise an address range assigned to an endpoint associated with thesecond host system; generating a work queue structure in the addressrange; posting, by the first host system, a socket initializationrequest to the work queue structure; retrieving, by the second hostsystem, the socket initialization request from the work queue structurevia the endpoint by performing a direct memory access (DMA) operation toretrieve the socket initialization request from the work queuestructure, wherein the socket initialization request contains a firstportion of parameters for establishing the socket communicationconnection; performing a DMA operation from the endpoint to a rootcomplex of the first host system to transfer a second portion ofparameters for establishing the socket communication connectionresponsive to the second host system accepting the socket communicationrequest; establishing a socket communication connection between thefirst host system and the second host system based on the socketinitialization request, the first portion of parameters, and the secondportion of parameters; and processing send and receive communicationsbetween the first host system and the second host system using theestablished socket communication connection.
 2. The method of claim 1,wherein initializing the memory address space in the shared memory ofthe first host system comprises processing vital product data (VPD)information for the endpoint, wherein the VPD information includes afield indicating whether the endpoint supports socket connections, andwherein the socket initialization request is posted to the work queuestructure only if the VPD information indicates that the endpointsupports socket connections.
 3. The method of claim 1, furthercomprising: performing a write operation to a doorbell structure in theshared memory in response to posting the socket initialization request;and polling, by the second host system, the doorbell structure todetermine if a socket initialization request is available for processingby the second host system.
 4. The method of claim 1, further comprising:parsing, by the second host system, the socket initialization request;determining, by the second host system, whether to accept or deny thesocket initialization request; and sending, by the second host system, aresponse to the first host system based on results of determiningwhether to accept or deny the socket initialization request.
 5. Themethod of claim 4, wherein the socket initialization request contains abase address, limit, and starting offset into the work queue structureto be used for the first portion of parameters for establishing thesocket communication connection.
 6. The method of claim 1, wherein thesecond portion of parameters for establishing the socket communicationconnection comprises a base address, limit, and starting offset into awork queue structure provided in a shared memory associated with thesecond host system.
 7. The method of claim 1, wherein the send andreceive operations comprise at least one of push operations or pulloperations in accordance with an established transaction protocol. 8.The method of claim 7, wherein the push operations and pull operationsare direct memory access (DMA) operations.
 9. The method of claim 1,wherein initializing the memory address space in a shared memory of thefirst host system comprises: traversing links in a communication fabricof the data processing system to gather information about endpoints androot complexes present in the communication fabric; generating at leastone virtual hierarchy identifying at least one endpoint and at least oneroot complex that are physically or logically associated with eachother; and initializing the memory address space based on the at leastone virtual hierarchy such that each endpoint associated with a rootcomplex of the first host system has a corresponding address range inthe memory address space.
 10. The method of claim 1, wherein the dataprocessing system is a blade server and the first host system and secondhost system are blades in the blade server.
 11. The method of claim 1,wherein the data processing system comprises a peripheral componentinterconnect express (PCIe) fabric to which the first host system andsecond host system are coupled, and wherein the endpoint is a PCIeadapter.
 12. The method of claim 11, wherein the PCIe fabric is amultiple root aware PCIe fabric comprising one or more multiple rootaware (MRA) switches.
 13. A computer program product comprising anon-transitory computer recordable medium having a computer readableprogram recorded thereon, wherein the computer readable program, whenexecuted in a data processing system, causes the data processing systemto: initialize a memory address space in a shared memory of the firsthost system to comprise an address range assigned to an endpointassociated with the second host system; generate a work queue structurein the address range; post, by the first host system, a socketinitialization request to the work queue structure; retrieve, by thesecond host system, the socket initialization request from the workqueue structure via the endpoint by performing a direct memory access(DMA) operation to retrieve the socket initialization request from thework queue structure, wherein the socket initialization request containsa first portion of parameters for establishing the socket communicationconnection; perform a DMA operation from the endpoint to a root complexof the first host system to transfer a second portion of parameters forestablishing the socket communication connection responsive to thesecond host system accepting the socket communication request; establisha socket communication connection between the first host system and thesecond host system based on the socket initialization request, the firstportion of parameters, and the second portion of parameters; and processsend and receive communications between the first host system and thesecond host system using the established socket communicationconnection.
 14. The computer program product of claim 13, wherein thecomputer readable program causes the data processing system toinitialize the memory address space in the shared memory of the firsthost system by processing vital product data (VPD) information for theendpoint, wherein the VPD information includes a field indicatingwhether the endpoint supports socket connections, and wherein the socketinitialization request is posted to the work queue structure only if theVPD information indicates that the endpoint supports socket connections.15. The computer program product of claim 13, wherein the computerreadable program further causes the data processing system to: perform awrite operation to a doorbell structure in the shared memory in responseto posting the socket initialization request; and poll, by the secondhost system, the doorbell structure to determine if a socketinitialization, request is available for processing by the second hostsystem.
 16. The computer program product of claim 13, wherein thecomputer readable program further causes the data processing system to:parse, by the second host system, the socket initialization request;determine, by the second host system, whether to accept or deny thesocket initialization request; and send, by the second host system, aresponse to the first host system based on results of determiningwhether to accept or deny the socket initialization request.
 17. Thecomputer program product of claim 13, wherein the socket initializationrequest contains a base address, limit, and starting offset into thework queue structure to be used for the first portion of parameters forestablishing the socket communication connection.
 18. The computerprogram product of claim 13, wherein the second portion of parametersfor establishing the socket communication connection comprises a baseaddress, limit, and starting offset into a work queue structure providedin a shared memory associated with the second host system.
 19. Thecomputer program product of claim 13, wherein the send and receiveoperations comprise at least one of push operations or pull operationsin accordance with an established transaction protocol.
 20. The computerprogram product of claim 19, wherein the push operations and pulloperations are direct memory access (DMA) operations.
 21. The computerprogram product of claim 13, wherein the computer readable programcauses the data processing system to initialize the memory address spacein a shared memory of the first host system by: traversing links in acommunication fabric of the data processing system to gather informationabout endpoints and root complexes present in the communication fabric;generating at least one virtual hierarchy identifying at least oneendpoint and at least one root complex that are physically or logicallyassociated with each other; and initializing the memory address spacebased on the at least one virtual hierarchy such that each endpointassociated with a root complex of the first host system has acorresponding address range in the memory address space.
 22. Thecomputer program product of claim 13, wherein the data processing systemis a blade server and the first host system and second host system areblades in the blade server.
 23. The computer program product of claim13, wherein the data processing system comprises a peripheral componentinterconnect express (PCIe) fabric to which the first host system andsecond host system are coupled, and wherein the endpoint is a PCIeadapter.
 24. The computer program product of claim 23, wherein the PCIefabric is a multiple root aware PCIe fabric comprising one or moremultiple root aware (MRA) switches.
 25. A data processing system,comprising: a first host system; a second host system; and acommunication fabric coupled to the first host system and the secondhost system, wherein: a memory address space in a shared memory of thefirst host system is initialized to comprise an address range assignedto an endpoint associated with the second host system; a work queuestructure is generated in the address range; a socket initializationrequest is posted, by the first host system, to the work queuestructure; the socket initialization request is retrieved, by the secondhost system, from the work queue structure via the endpoint byperforming a direct memory access (DMA) operation to retrieve the socketinitialization request from the work queue structure, wherein the socketinitialization request contains a first portion of parameters forestablishing the socket communication connection; a DMA operation isperformed from the endpoint to a root complex of the first host systemto transfer a second portion of parameters for establishing the socketcommunication connection responsive to the second host system acceptingthe socket communication request; a socket communication connection isestablished between the first host system and the second host systembased on the socket initialization request, the first portion ofparameters, and the second portion of parameters; and send and receivecommunications between the first host system and the second host systemare processed using the established socket communication connection. 26.The data processing system of claim 25, wherein the memory address spacein the shared memory of the first host system is initialized byprocessing vital product data (VPD) information for the endpoint,wherein the VPD information includes a field indicating whether theendpoint supports socket connections, and wherein the socketinitialization request is posted to the work queue structure only if theVPD information indicates that the endpoint supports socket connections.27. The data processing system of claim 25, wherein: a write operationis performed to a doorbell structure in the shared memory in response toposting the socket initialization request; and the doorbell structure ispolled, by the second host system, to determine if a socketinitialization request is available for processing by the second hostsystem.
 28. The data processing system of claim 25, wherein the secondhost system: parses the socket initialization request; determineswhether to accept or deny the socket initialization request; and sends aresponse to the first host system based on results of determiningwhether to accept or deny the socket initialization request.
 29. Thedata processing system of claim 28, wherein the socket initializationrequest contains a base address, limit, and starting offset into thework queue structure to be used for the first portion of parameters forestablishing the socket communication connection.
 30. The dataprocessing system of claim 25, wherein the second portion of parametersfor establishing the socket communication connection comprises a baseaddress, limit, and starting offset into a work queue structure providedin a shared memory associated with the second host system.
 31. The dataprocessing system of claim 25, wherein the memory address space in theshared memory of the first host system is initialized by: traversinglinks in a communication fabric of the data processing system to gatherinformation about endpoints and root complexes present in thecommunication fabric; generating at least one virtual hierarchyidentifying at least one endpoint and at least one root complex that arephysically or logically associated with each other; and initializing thememory address space based on the at least one virtual hierarchy suchthat each endpoint associated with a root complex of the first hostsystem has a corresponding address range in the memory address space.32. The data processing system of claim 25, wherein the data processingsystem is a blade server and the first host system and second hostsystem are blades in the blade server.